Primary pucch tpc index and a secondary pucch tpc index in a wireless network

ABSTRACT

A wire device receives: configuration parameters of: a primary cell with a primary physical uplink control channel (PUCCH); and a secondary cell with a secondary PUCCH; a transmit power control (TPC) radio network temporary identifier (RNTI); a primary TPC index of the primary PUCCH; and a secondary TPC index of the secondary PUCCH. The wireless device receives a downlink control information (DCI) associated with the TPC RNTI. The secondary TPC index identifies a TPC command in an array of TPC commands in the DCI. The wireless device adjusts a transmission power of the secondary PUCCH based on the TPC command.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No. 17/196,604, filed Mar. 9, 2021, which is a continuation of U.S. Pat. No. 10,979,928, issued Apr. 13, 2021, which is a continuation of U.S. Pat. No. 10,631,191, issued Apr. 21, 2020, which is a continuation of U.S. Pat. No. 10,257,741, issued Apr. 9, 2019, which is a continuation of U.S. Pat. No. 9,992,700, issued Jun. 5, 2018, which is a continuation of U.S. Pat. No. 9,629,095, issued Apr. 18, 2017, which claims the benefit of U.S. Provisional Application No. 62/137,537, filed Mar. 24, 2015, which is hereby incorporated by reference in its entirety.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Examples of several of the various embodiments of the present invention are described herein with reference to the drawings.

FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per an aspect of an embodiment of the present invention.

FIG. 2 is a diagram depicting an example transmission time and reception time for two carriers in a carrier group as per an aspect of an embodiment of the present invention.

FIG. 3 is a diagram depicting OFDM radio resources as per an aspect of an embodiment of the present invention.

FIG. 4 is a block diagram of a base station and a wireless device as per an aspect of an embodiment of the present invention.

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D are example diagrams for uplink and downlink signal transmission as per an aspect of an embodiment of the present invention.

FIG. 6 is an example diagram for a protocol structure with CA and DC as per an aspect of an embodiment of the present invention.

FIG. 7 is an example diagram for a protocol structure with CA and DC as per an aspect of an embodiment of the present invention.

FIG. 8 shows example TAG configurations as per an aspect of an embodiment of the present invention.

FIG. 9 is an example message flow in a random access process in a secondary TAG as per an aspect of an embodiment of the present invention.

FIG. 10 is an example grouping of cells into PUCCH groups as per an aspect of an embodiment of the present invention.

FIG. 11 illustrates example groupings of cells into one or more PUCCH groups and one or more TAGs as per an aspect of an embodiment of the present invention.

FIG. 12 illustrates example groupings of cells into one or more PUCCH groups and one or more TAGs as per an aspect of an embodiment of the present invention.

FIG. 13 is an example MAC PDU as per an aspect of an embodiment of the present invention.

FIG. 14 is an example flow diagram as per an aspect of an embodiment of the present invention.

FIG. 15 is an example flow diagram as per an aspect of an embodiment of the present invention.

FIG. 16 is an example flow diagram as per an aspect of an embodiment of the present invention.

DETAILED DESCRIPTION OF EMBODIMENTS

Example embodiments of the present invention enable operation of multiple physical uplink control channel (PUCCH) groups. Embodiments of the technology disclosed herein may be employed in the technical field of multicarrier communication systems. More particularly, the embodiments of the technology disclosed herein may relate to operation of PUCCH groups.

The following Acronyms are used throughout the present disclosure:

ASIC application-specific integrated circuit

BPSK binary phase shift keying

CA carrier aggregation

CSI channel state information

CDMA code division multiple access

CSS common search space

CPLD complex programmable logic devices

CC component carrier

DL downlink

DCI downlink control information

DC dual connectivity

EPC evolved packet core

E-UTRAN evolved-universal terrestrial radio access network

FPGA field programmable gate arrays

FDD frequency division multiplexing

HDL hardware description languages

HARQ hybrid automatic repeat request

IE information element

LTE long term evolution

MCG master cell group

MeNB master evolved node B

MIB master information block

MAC media access control

MAC media access control

MME mobility management entity

NAS non-access stratum

OFDM orthogonal frequency division multiplexing

PDCP packet data convergence protocol

PDU packet data unit

PHY physical

PDCCH physical downlink control channel

PHICH physical HARQ indicator channel

PUCCH physical uplink control channel

PUSCH physical uplink shared channel

PCell primary cell

PCell primary cell

PCC primary component carrier

PSCell primary secondary cell

pTAG primary timing advance group

QAM quadrature amplitude modulation

QPSK quadrature phase shift keying

RBG Resource Block Groups

RLC radio link control

RRC radio resource control

RA random access

RB resource blocks

SCC secondary component carrier

SCell secondary cell

Scell secondary cells

SCG secondary cell group

SeNB secondary evolved node B

sTAGs secondary timing advance group

SDU service data unit

S-GW serving gateway

SRB signaling radio bearer

SC-OFDM single carrier-OFDM

SFN system frame number

SIB system information block

TAI tracking area identifier

TAT time alignment timer

TDD time division duplexing

TDMA time division multiple access

TA timing advance

TAG timing advance group

TB transport block

UL uplink

UE user equipment

VHDL VHSIC hardware description language

Example embodiments of the invention may be implemented using various physical layer modulation and transmission mechanisms. Example transmission mechanisms may include, but are not limited to: CDMA, OFDM, TDMA, Wavelet technologies, and/or the like. Hybrid transmission mechanisms such as TDMA/CDMA, and OFDM/CDMA may also be employed. Various modulation schemes may be applied for signal transmission in the physical layer. Examples of modulation schemes include, but are not limited to: phase, amplitude, code, a combination of these, and/or the like. An example radio transmission method may implement QAM using BPSK, QPSK, 16-QAM, 64-QAM, 256-QAM, and/or the like. Physical radio transmission may be enhanced by dynamically or semi-dynamically changing the modulation and coding scheme depending on transmission requirements and radio conditions.

FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per an aspect of an embodiment of the present invention. As illustrated in this example, arrow(s) in the diagram may depict a subcarrier in a multicarrier OFDM system. The OFDM system may use technology such as OFDM technology, SC-OFDM technology, or the like. For example, arrow 101 shows a subcarrier transmitting information symbols. FIG. 1 is for illustration purposes, and a typical multicarrier OFDM system may include more subcarriers in a carrier. For example, the number of subcarriers in a carrier may be in the range of 10 to 10,000 subcarriers. FIG. 1 shows two guard bands 106 and 107 in a transmission band. As illustrated in FIG. 1 , guard band 106 is between subcarriers 103 and subcarriers 104. The example set of subcarriers A 102 includes subcarriers 103 and subcarriers 104. FIG. 1 also illustrates an example set of subcarriers B 105. As illustrated, there is no guard band between any two subcarriers in the example set of subcarriers B 105. Carriers in a multicarrier OFDM communication system may be contiguous carriers, non-contiguous carriers, or a combination of both contiguous and non-contiguous carriers.

FIG. 2 is a diagram depicting an example transmission time and reception time for two carriers as per an aspect of an embodiment of the present invention. A multicarrier OFDM communication system may include one or more carriers, for example, ranging from 1 to 10 carriers. Carrier A 204 and carrier B 205 may have the same or different timing structures. Although FIG. 2 shows two synchronized carriers, carrier A 204 and carrier B 205 may or may not be synchronized with each other. Different radio frame structures may be supported for FDD and TDD duplex mechanisms. FIG. 2 shows an example FDD frame timing. Downlink and uplink transmissions may be organized into radio frames 201. In this example, radio frame duration is 10 msec. Other frame durations, for example, in the range of 1 to 100 msec may also be supported. In this example, each 10 ms radio frame 201 may be divided into ten equally sized subframes 202. Other subframe durations such as including 0.5 msec, 1 msec, 2 msec, and 5 msec may also be supported. Subframe(s) may consist of two or more slots (e.g. slots 206 and 207). For the example of FDD, 10 subframes may be available for downlink transmission and 10 subframes may be available for uplink transmissions in each 10 ms interval. Uplink and downlink transmissions may be separated in the frequency domain. Slot(s) may include a plurality of OFDM symbols 203. The number of OFDM symbols 203 in a slot 206 may depend on the cyclic prefix length and subcarrier spacing.

FIG. 3 is a diagram depicting OFDM radio resources as per an aspect of an embodiment of the present invention. The resource grid structure in time 304 and frequency 305 is illustrated in FIG. 3 . The quantity of downlink subcarriers or RBs (in this example 6 to 100 RBs) may depend, at least in part, on the downlink transmission bandwidth 306 configured in the cell. The smallest radio resource unit may be called a resource element (e.g. 301). Resource elements may be grouped into resource blocks (e.g. 302). Resource blocks may be grouped into larger radio resources called Resource Block Groups (RBG) (e.g. 303). The transmitted signal in slot 206 may be described by one or several resource grids of a plurality of subcarriers and a plurality of OFDM symbols. Resource blocks may be used to describe the mapping of certain physical channels to resource elements. Other pre-defined groupings of physical resource elements may be implemented in the system depending on the radio technology. For example, 24 subcarriers may be grouped as a radio block for a duration of 5 msec. In an illustrative example, a resource block may correspond to one slot in the time domain and 180 kHz in the frequency domain (for 15 KHz subcarrier bandwidth and 12 subcarriers).

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D are example diagrams for uplink and downlink signal transmission as per an aspect of an embodiment of the present invention. FIG. 5A shows an example uplink physical channel. The baseband signal representing the physical uplink shared channel may perform the following processes. These functions are illustrated as examples and it is anticipated that other mechanisms may be implemented in various embodiments. The functions may comprise scrambling, modulation of scrambled bits to generate complex-valued symbols, mapping of the complex-valued modulation symbols onto one or several transmission layers, transform precoding to generate complex-valued symbols, precoding of the complex-valued symbols, mapping of precoded complex-valued symbols to resource elements, generation of complex-valued time-domain SC-FDMA signal for each antenna port, and/or the like.

Example modulation and up-conversion to the carrier frequency of the complex-valued SC-FDMA baseband signal for each antenna port and/or the complex-valued PRACH baseband signal is shown in FIG. 5B. Filtering may be employed prior to transmission.

An example structure for Downlink Transmissions is shown in FIG. 5C. The baseband signal representing a downlink physical channel may perform the following processes. These functions are illustrated as examples and it is anticipated that other mechanisms may be implemented in various embodiments. The functions include scrambling of coded bits in each of the codewords to be transmitted on a physical channel; modulation of scrambled bits to generate complex-valued modulation symbols; mapping of the complex-valued modulation symbols onto one or several transmission layers; precoding of the complex-valued modulation symbols on each layer for transmission on the antenna ports; mapping of complex-valued modulation symbols for each antenna port to resource elements; generation of complex-valued time-domain OFDM signal for each antenna port, and/or the like.

Example modulation and up-conversion to the carrier frequency of the complex-valued OFDM baseband signal for each antenna port is shown in FIG. 5D. Filtering may be employed prior to transmission.

FIG. 4 is an example block diagram of a base station 401 and a wireless device 406, as per an aspect of an embodiment of the present invention. A communication network 400 may include at least one base station 401 and at least one wireless device 406. The base station 401 may include at least one communication interface 402, at least one processor 403, and at least one set of program code instructions 405 stored in non-transitory memory 404 and executable by the at least one processor 403. The wireless device 406 may include at least one communication interface 407, at least one processor 408, and at least one set of program code instructions 410 stored in non-transitory memory 409 and executable by the at least one processor 408. Communication interface 402 in base station 401 may be configured to engage in communication with communication interface 407 in wireless device 406 via a communication path that includes at least one wireless link 411. Wireless link 411 may be a bi-directional link. Communication interface 407 in wireless device 406 may also be configured to engage in a communication with communication interface 402 in base station 401. Base station 401 and wireless device 406 may be configured to send and receive data over wireless link 411 using multiple frequency carriers. According to some of the various aspects of embodiments, transceiver(s) may be employed. A transceiver is a device that includes both a transmitter and receiver. Transceivers may be employed in devices such as wireless devices, base stations, relay nodes, and/or the like. Example embodiments for radio technology implemented in communication interface 402, 407 and wireless link 411 are illustrated are FIG. 1 , FIG. 2 , FIG. 3 , FIG. 5 , and associated text.

An interface may be a hardware interface, a firmware interface, a software interface, and/or a combination thereof. The hardware interface may include connectors, wires, electronic devices such as drivers, amplifiers, and/or the like. A software interface may include code stored in a memory device to implement protocol(s), protocol layers, communication drivers, device drivers, combinations thereof, and/or the like. A firmware interface may include a combination of embedded hardware and code stored in and/or in communication with a memory device to implement connections, electronic device operations, protocol(s), protocol layers, communication drivers, device drivers, hardware operations, combinations thereof, and/or the like.

The term configured may relate to the capacity of a device whether the device is in an operational or non-operational state. Configured may also refer to specific settings in a device that effect the operational characteristics of the device whether the device is in an operational or non-operational state. In other words, the hardware, software, firmware, registers, memory values, and/or the like may be “configured” within a device, whether the device is in an operational or nonoperational state, to provide the device with specific characteristics. Terms such as “a control message to cause in a device” may mean that a control message has parameters that may be used to configure specific characteristics in the device, whether the device is in an operational or non-operational state.

According to some of the various aspects of embodiments, an LTE network may include a multitude of base stations, providing a user plane PDCP/RLC/MAC/PHY and control plane (RRC) protocol terminations towards the wireless device. The base station(s) may be interconnected with other base station(s) (e.g. employing an X2 interface). The base stations may also be connected employing, for example, an S1 interface to an EPC. For example, the base stations may be interconnected to the MME employing the S1-MME interface and to the S-G) employing the S1-U interface. The S1 interface may support a many-to-many relation between MMEs/Serving Gateways and base stations. A base station may include many sectors for example: 1, 2, 3, 4, or 6 sectors. A base station may include many cells, for example, ranging from 1 to 50 cells or more. A cell may be categorized, for example, as a primary cell or secondary cell. At RRC connection establishment/re-establishment/handover, one serving cell may provide the NAS (non-access stratum) mobility information (e.g. TAI), and at RRC connection re-establishment/handover, one serving cell may provide the security input. This cell may be referred to as the Primary Cell (PCell). In the downlink, the carrier corresponding to the PCell may be the Downlink Primary Component Carrier (DL PCC), while in the uplink, it may be the Uplink Primary Component Carrier (UL PCC). Depending on wireless device capabilities, Secondary Cells (SCells) may be configured to form together with the PCell a set of serving cells. In the downlink, the carrier corresponding to an SCell may be a Downlink Secondary Component Carrier (DL SCC), while in the uplink, it may be an Uplink Secondary Component Carrier (UL SCC). An SCell may or may not have an uplink carrier.

A cell, comprising a downlink carrier and optionally an uplink carrier, may be assigned a physical cell ID and a cell index. A carrier (downlink or uplink) may belong to only one cell. The cell ID or Cell index may also identify the downlink carrier or uplink carrier of the cell (depending on the context it is used). In the specification, cell ID may be equally referred to a carrier ID, and cell index may be referred to carrier index. In implementation, the physical cell ID or cell index may be assigned to a cell. A cell ID may be determined using a synchronization signal transmitted on a downlink carrier. A cell index may be determined using RRC messages. For example, when the specification refers to a first physical cell ID for a first downlink carrier, the specification may mean the first physical cell ID is for a cell comprising the first downlink carrier. The same concept may apply to, for example, carrier activation. When the specification indicates that a first carrier is activated, the specification may equally mean that the cell comprising the first carrier is activated.

Embodiments may be configured to operate as needed. The disclosed mechanism may be performed when certain criteria are met, for example, in a wireless device, a base station, a radio environment, a network, a combination of the above, and/or the like. Example criteria may be based, at least in part, on for example, traffic load, initial system set up, packet sizes, traffic characteristics, a combination of the above, and/or the like. When the one or more criteria are met, various example embodiments may be applied. Therefore, it may be possible to implement example embodiments that selectively implement disclosed protocols.

A base station may communicate with a mix of wireless devices. Wireless devices may support multiple technologies, and/or multiple releases of the same technology. Wireless devices may have some specific capability(ies) depending on its wireless device category and/or capability(ies). A base station may comprise multiple sectors. When this disclosure refers to a base station communicating with a plurality of wireless devices, this disclosure may refer to a subset of the total wireless devices in a coverage area. This disclosure may refer to, for example, a plurality of wireless devices of a given LTE release with a given capability and in a given sector of the base station. The plurality of wireless devices in this disclosure may refer to a selected plurality of wireless devices, and/or a subset of total wireless devices in a coverage area which perform according to disclosed methods, and/or the like. There may be a plurality of wireless devices in a coverage area that may not comply with the disclosed methods, for example, because those wireless devices perform based on older releases of LTE technology.

FIG. 6 and FIG. 7 are example diagrams for protocol structure with CA and DC as per an aspect of an embodiment of the present invention. E-UTRAN may support Dual Connectivity (DC) operation whereby a multiple RX/TX UE in RRC CONNECTED may be configured to utilize radio resources provided by two schedulers located in two eNBs connected via a non-ideal backhaul over the X2 interface. eNBs involved in DC for a certain UE may assume two different roles: an eNB may either act as an MeNB or as an SeNB. In DC a UE may be connected to one MeNB and one SeNB. Mechanisms implemented in DC may be extended to cover more than two eNBs. FIG. 7 illustrates one example structure for the UE side MAC entities when a Master Cell Group (MCG) and a Secondary Cell Group (SCG) are configured, and it may not restrict implementation. Media Broadcast Multicast Service (MBMS) reception is not shown in this figure for simplicity.

In DC, the radio protocol architecture that a particular bearer uses may depend on how the bearer is setup. Three alternatives may exist, an MCG bearer, an SCG bearer and a split bearer as shown in FIG. 6 . RRC may be located in MeNB and SRBs may be configured as a MCG bearer type and may use the radio resources of the MeNB. DC may also be described as having at least one bearer configured to use radio resources provided by the SeNB. DC may or may not be configured/implemented in example embodiments of the invention.

In the case of DC, the UE may be configured with two MAC entities: one MAC entity for MeNB, and one MAC entity for SeNB. In DC, the configured set of serving cells for a UE may comprise of two subsets: the Master Cell Group (MCG) containing the serving cells of the MeNB, and the Secondary Cell Group (SCG) containing the serving cells of the SeNB. For a SCG, one or more of the following may be applied: at least one cell in the SCG has a configured UL CC and one of them, named PSCell (or PCell of SCG, or sometimes called PCell), is configured with PUCCH resources; when the SCG is configured, there may be at least one SCG bearer or one Split bearer; upon detection of a physical layer problem or a random access problem on a PSCell, or the maximum number of RLC retransmissions has been reached associated with the SCG, or upon detection of an access problem on a PSCell during a SCG addition or a SCG change: a RRC connection re-establishment procedure may not be triggered, UL transmissions towards cells of the SCG are stopped, a MeNB may be informed by the UE of a SCG failure type, for split bearer, the DL data transfer over the MeNB is maintained; the RLC AM bearer may be configured for the split bearer; like PCell, PSCell may not be de-activated; PSCell may be changed with a SCG change (e.g. with security key change and a RACH procedure); and/or neither a direct bearer type change between a Split bearer and a SCG bearer nor simultaneous configuration of a SCG and a Split bearer are supported.

With respect to the interaction between a MeNB and a SeNB, one or more of the following principles may be applied: the MeNB may maintain the RRM measurement configuration of the UE and may, (e.g., based on received measurement reports or traffic conditions or bearer types), decide to ask a SeNB to provide additional resources (serving cells) for a UE; upon receiving a request from the MeNB, a SeNB may create a container that may result in the configuration of additional serving cells for the UE (or decide that it has no resource available to do so); for UE capability coordination, the MeNB may provide (part of) the AS configuration and the UE capabilities to the SeNB; the MeNB and the SeNB may exchange information about a UE configuration by employing of RRC containers (inter-node messages) carried in X2 messages; the SeNB may initiate a reconfiguration of its existing serving cells (e.g., PUCCH towards the SeNB); the SeNB may decide which cell is the PSCell within the SCG; the MeNB may not change the content of the RRC configuration provided by the SeNB; in the case of a SCG addition and a SCG SCell addition, the MeNB may provide the latest measurement results for the SCG cell(s); both a MeNB and a SeNB may know the SFN and subframe offset of each other by OAM, (e.g., for the purpose of DRX alignment and identification of a measurement gap). In an example, when adding a new SCG SCell, dedicated RRC signalling may be used for sending required system information of the cell as for CA, except for the SFN acquired from a MIB of the PSCell of a SCG.

According to some of the various aspects of embodiments, serving cells having an uplink to which the same time alignment (TA) applies may be grouped in a TA group (TAG). Serving cells in one TAG may use the same timing reference. For a given TAG, user equipment (UE) may use one downlink carrier as a timing reference at a given time. The UE may use a downlink carrier in a TAG as a timing reference for that TAG. For a given TAG, a UE may synchronize uplink subframe and frame transmission timing of uplink carriers belonging to the same TAG. According to some of the various aspects of embodiments, serving cells having an uplink to which the same TA applies may correspond to serving cells hosted by the same receiver. A TA group may comprise at least one serving cell with a configured uplink. A UE supporting multiple TAs may support two or more TA groups. One TA group may contain the PCell and may be called a primary TAG (pTAG). In a multiple TAG configuration, at least one TA group may not contain the PCell and may be called a secondary TAG (sTAG). Carriers within the same TA group may use the same TA value and the same timing reference. When DC is configured, cells belonging to a cell group (MCG or SCG) may be grouped into multiple TAGs including a pTAG and one or more sTAGs.

FIG. 8 shows example TAG configurations as per an aspect of an embodiment of the present invention. In Example 1, pTAG comprises PCell, and an sTAG comprises SCell1. In Example 2, a pTAG comprises a PCell and SCell1, and an sTAG comprises SCell2 and SCell3. In Example 3, pTAG comprises PCell and SCell1, and an sTAG1 includes SCell2 and SCell3, and sTAG2 comprises SCell4. Up to four TAGs may be supported in a cell group (MCG or SCG) and other example TAG configurations may also be provided. In various examples in this disclosure, example mechanisms are described for a pTAG and an sTAG. The operation with one example sTAG is described, and the same operation may be applicable to other sTAGs. The example mechanisms may be applied to configurations with multiple sTAGs.

According to some of the various aspects of embodiments, TA maintenance, pathloss reference handling and a timing reference for a pTAG may follow LTE release 10 principles in the MCG and/or SCG. The UE may need to measure downlink pathloss to calculate uplink transmit power. A pathloss reference may be used for uplink power control and/or transmission of random access preamble(s). UE may measure downlink pathloss using signals received on a pathloss reference cell. For SCell(s) in a pTAG, the choice of a pathloss reference for cells may be selected from and/or be limited to the following two options: a) the downlink SCell linked to an uplink SCell using system information block 2 (SIB2), and b) the downlink pCell. The pathloss reference for SCells in a pTAG may be configurable using RRC message(s) as a part of an SCell initial configuration and/or reconfiguration. According to some of the various aspects of embodiments, a PhysicalConfigDedicatedSCell information element (IE) of an SCell configuration may include a pathloss reference SCell (downlink carrier) for an SCell in a pTAG. The downlink SCell linked to an uplink SCell using system information block 2 (SIB2) may be referred to as the SIB2 linked downlink of the SCell. Different TAGs may operate in different bands. For an uplink carrier in an sTAG, the pathloss reference may be only configurable to the downlink SCell linked to an uplink SCell using the system information block 2 (SIB2) of the SCell.

To obtain initial uplink (UL) time alignment for an sTAG, an eNB may initiate an RA procedure. In an sTAG, a UE may use one of any activated SCells from this sTAG as a timing reference cell. In an example embodiment, the timing reference for SCells in an sTAG may be the SIB2 linked downlink of the SCell on which the preamble for the latest RA procedure was sent. There may be one timing reference and one time alignment timer (TAT) per TA group. A TAT for TAGs may be configured with different values. In a MAC entity, when a TAT associated with a pTAG expires: all TATs may be considered as expired, the UE may flush HARQ buffers of serving cells, the UE may clear any configured downlink assignment/uplink grants, and the RRC in the UE may release PUCCH/SRS for all configured serving cells. When the pTAG TAT is not running, an sTAG TAT may not be running. When the TAT associated with an sTAG expires: a) SRS transmissions may be stopped on the corresponding SCells, b) SRS RRC configuration may be released, c) CSI reporting configuration for corresponding SCells may be maintained, and/or d) the MAC in the UE may flush the uplink HARQ buffers of the corresponding SCells.

An eNB may initiate an RA procedure via a PDCCH order for an activated SCell. This PDCCH order may be sent on a scheduling cell of this SCell. When cross carrier scheduling is configured for a cell, the scheduling cell may be different than the cell that is employed for preamble transmission, and the PDCCH order may include an SCell index. At least a non-contention based RA procedure may be supported for SCell(s) assigned to sTAG(s).

FIG. 9 is an example message flow in a random access process in a secondary TAG as per an aspect of an embodiment of the present invention. An eNB transmits an activation command 600 to activate an SCell. A preamble 602 (Msg1) may be sent by a UE in response to a PDCCH order 601 on an SCell belonging to an sTAG. In an example embodiment, preamble transmission for SCells may be controlled by the network using PDCCH format 1A. Msg2 message 603 (RAR: random access response) in response to the preamble transmission on the SCell may be addressed to RA-RNTI in a PCell common search space (CSS). Uplink packets 604 may be transmitted on the SCell in which the preamble was transmitted.

According to some of the various aspects of embodiments, initial timing alignment may be achieved through a random access procedure. This may involve a UE transmitting a random access preamble and an eNB responding with an initial TA command NTA (amount of timing advance) within a random access response window. The start of the random access preamble may be aligned with the start of a corresponding uplink subframe at the UE assuming NTA=0. The eNB may estimate the uplink timing from the random access preamble transmitted by the UE. The TA command may be derived by the eNB based on the estimation of the difference between the desired UL timing and the actual UL timing. The UE may determine the initial uplink transmission timing relative to the corresponding downlink of the sTAG on which the preamble is transmitted.

The mapping of a serving cell to a TAG may be configured by a serving eNB with RRC signaling. The mechanism for TAG configuration and reconfiguration may be based on RRC signaling. According to some of the various aspects of embodiments, when an eNB performs an SCell addition configuration, the related TAG configuration may be configured for the SCell. In an example embodiment, an eNB may modify the TAG configuration of an SCell by removing (releasing) the SCell and adding(configuring) a new SCell (with the same physical cell ID and frequency) with an updated TAG ID. The new SCell with the updated TAG ID may initially be inactive subsequent to being assigned the updated TAG ID. The eNB may activate the updated new SCell and start scheduling packets on the activated SCell. In an example implementation, it may not be possible to change the TAG associated with an SCell, but rather, the SCell may need to be removed and a new SCell may need to be added with another TAG. For example, if there is a need to move an SCell from an sTAG to a pTAG, at least one RRC message, for example, at least one RRC reconfiguration message, may be send to the UE to reconfigure TAG configurations by releasing the SCell and then configuring the SCell as a part of the pTAG (when an SCell is added/configured without a TAG index, the SCell may be explicitly assigned to the pTAG). The PCell may not change its TA group and may always be a member of the pTAG.

The purpose of an RRC connection reconfiguration procedure may be to modify an RRC connection, (e.g. to establish, modify and/or release RBs, to perform handover, to setup, modify, and/or release measurements, to add, modify, and/or release SCells). If the received RRC Connection Reconfiguration message includes the sCellToReleaseList, the UE may perform an SCell release. If the received RRC Connection Reconfiguration message includes the sCellToAddModList, the UE may perform SCell additions or modification.

In LTE Release-10 and Release-11 CA, a PUCCH is only transmitted on the PCell (PSCell) to an eNB. In LTE-Release 12 and earlier, a UE may transmit PUCCH information on one cell (PCell or PSCell) to a given eNB.

As the number of CA capable UEs and also the number of aggregated carriers increase, the number of PUCCHs and also the PUCCH payload size may increase. Accommodating the PUCCH transmissions on the PCell may lead to a high PUCCH load on the PCell. A PUCCH on an SCell may be introduced to offload the PUCCH resource from the PCell. More than one PUCCH may be configured for example, a PUCCH on a PCell and another PUCCH on an SCell. FIG. 10 is an example grouping of cells into PUCCH groups as per an aspect of an embodiment of the present invention. In the example embodiments, one, two or more cells may be configured with PUCCH resources for transmitting CSI/ACK/NACK to a base station. Cells may be grouped into multiple PUCCH groups, and one or more cell within a group may be configured with a PUCCH. In an example configuration, one SCell may belong to one PUCCH group. SCells with a configured PUCCH transmitted to a base station may be called a PUCCH SCell, and a cell group with a common PUCCH resource transmitted to the same base station may be called a PUCCH group.

In Release-12, a PUCCH can be configured on a PCell and/or a PSCell, but cannot be configured on other SCells. In an example embodiment, a UE may transmit a message indicating that the UE supports PUCCH configuration on a PCell and SCell. Such an indication may be separate from an indication of of dual connectivity support by the UE. In an example embodiment, a UE may support both DC and PUCCH groups. In an example embodiment, either DC or PUCCH groups may be configured, but not both. In another example embodiment, more complicated configurations comprising both DC and PUCCH groups may be supported.

When a UE is capable of configuring PUCCH groups, and if a UE indicates that it supports simultaneous PUCCH/PUSCH transmission capability, it may imply that the UE supports simultaneous PUCCH/PUSCH transmission on both PCell and SCell. When multiple PUCCH groups are configured, a PUCCH may be configured or not configured with simultaneous PUCCH/PUSCH transmission.

In an example embodiment, PUCCH transmission to a base station on two serving cells may be realized as shown in FIG. 10 . A first group of cells may employ a PUCCH on the PCell and may be called PUCCH group 1 or a primary PUCCH group. A second group of cells may employ a PUCCH on an SCell and may be called PUCCH group 2 or a secondary PUCCH group. One, two or more PUCCH groups may be configured. In an example, cells may be grouped into two PUCCH groups, and each PUCCH group may include a cell with PUCCH resources. A PCell may provide PUCCH resources for the primary PUCCH group and an SCell in the secondary PUCCH group may provide PUCCH resources for the cells in the secondary PUCCH group. In an example embodiment, no cross-carrier scheduling between cells in different PUCCH groups may be configured. When cross-carrier scheduling between cells in different PUCCH groups is not configured, ACK/NACK on PHICH channel may be limited within a PUCCH group. Both downlink and uplink scheduling activity may be separate between cells belonging to different PUCCH groups.

A PUCCH on an SCell may carry HARQ-ACK and CSI information. A PCell may be configured with PUCCH resources. In an example embodiment, RRC parameters for an SCell PUCCH Power Control for a PUCCH on an SCell may be different from those of a PCell PUCCH. A Transmit Power Control command for a PUCCH on an SCell may be transmitted in DCI(s) on the SCell carrying the PUCCH.

UE procedures on a PUCCH transmission may be different and/or independent between PUCCH groups. For example, determination of DL HARQ-ACK timing, PUCCH resource determination for HARQ-ACK and/or CSI, Higher-layer configuration of simultaneous HARQ-ACK+CSI on a PUCCH, Higher-layer configuration of simultaneous HARQ-ACK+SRS in one subframe may be configured differently for a PUCCH PCell and a PUCCH SCell.

A PUCCH group may be a group of serving cells configured by a RRC and use the same serving cell in the group for transmission of a PUCCH. A Primary PUCCH group may be a PUCCH group containing a PCell. A secondary PUCCH group may be a PUCCH cell group not containing the PCell. In an example embodiment, an SCell may belong to one PUCCH group. When one SCell belongs to a PUCCH group, ACK/NACK or CSI for that SCell may be transmitted over the PUCCH in that PUCCH group (over PUCCH SCell or PUCCH PCell). A PUCCH on an SCell may reduce the PUCCH load on the PCell. A PUCCH SCell may be employed for UCI transmission of SCells in the corresponding PUCCH group.

In an example embodiment, a flexible PUCCH configuration in which control signalling is sent on one, two or more PUCCHs may be possible. Beside the PCell, it may be possible to configure a selected number of SCells for PUCCH transmission (herein called PUCCH SCells). Control signalling information conveyed in a certain PUCCH SCell may be related to a set of SCells in a corresponding PUCCH group that are configured by the network via RRC signalling.

PUCCH control signalling carried by a PUCCH channel may be distributed between a PCell and SCells for off-loading or robustness purposes. By enabling a PUCCH in an SCell, it may be possible to distribute the overall CSI reports for a given UE between a PCell and a selected number of SCells (e.g. PUCCH SCells), thereby limiting PUCCH CSI resource consumption by a given UE on a certain cell. It may be possible to map CSI reports for a certain SCell to a selected PUCCH SCell. An SCell may be assigned a certain periodicity and time-offset for transmission of control information. Periodic CSI for a serving cell may be mapped on a PUCCH (on the PCell or on a PUCCH-SCell) via RRC signalling. The possibility of distributing CSI reports, HARQ feedbacks, and/or Scheduling Requests across PUCCH SCells may provide flexibility and capacity improvements. HARQ feedback for a serving cell may be mapped on a PUCCH (on the PCell or on a PUCCH SCell) via RRC signalling.

In example embodiments, PUCCH transmission may be configured on a PCell, as well as one SCell in CA. An SCell PUCCH may be realized using the concept of PUCCH groups, where aggregated cells are grouped into two or more PUCCH groups. One cell from a PUCCH group may be configured to carry a PUCCH. More than 5 carriers may be configured. In the example embodiments, up to n carriers may be aggregated. For example, n may be 16, 32, or 64. Some CCs may have non-backward compatible configurations supporting only advanced UEs (e.g. support licensed assisted access SCells). In an example embodiment, one SCell PUCCH (e.g. two PUCCH groups) may be supported. In another example embodiment, a PUCCH group concept with multiple (more than one) SCells carrying PUCCH may be employed (e.g., there can be more than two PUCCH groups).

In an example embodiment, a given PUCCH group may not comprise serving cells of both MCG and SCG. One of the PUCCHs may be configured on the PCell. In an example embodiment, PUCCH mapping of serving cells may be configured by RRC messages. In an example embodiment, a maximum value of an SCellIndex and a ServCellIndex may be 31 (ranging from 0 to 31). In an example, a maximum value of stag-Id may be 3. The CIF for a scheduled cell may be configured explicitly. A PUCCH SCell may be configured by giving a PUCCH configuration for an SCell. A HARQ feedback and CSI report of a PUCCH SCell may be sent on the PUCCH of that PUCCH SCell. The HARQ feedback and CSI report of a SCell may sent on a PUCCH of a PCell if no PUCCH SCell is signalled for that SCell. The HARQ feedback and CSI report of an SCell may be sent on the PUCCH of one PUCCH SCell; hence they may not be sent on the PUCCH of different PUCCH SCell. The UE may report a Type 2 PH for serving cells configured with a PUCCH. In an example embodiment, a MAC activation/deactivation may be supported for a PUCCH SCell. An eNB may manage the activation/deactivation status for SCells. A newly added PUCCH SCell may be initially deactivated.

In an example embodiment, independent configuration of PUCCH groups and TAGs may be supported. FIG. 11 and FIG. 12 show example configurations of TAGs and PUCCH groups. For example, one TAG may contain multiple serving cells with a PUCCH. For example, each TAG may only comprise cells of one PUCCH group. For example, a TAG may comprise the serving cells (without a PUCCH) which belong to different PUCCH groups.

There may not be a one-to-one mapping between TAGs and PUCCH groups. For example, in a configuration, a PUCCH SCell may belong to primary TAG. In an example implementation, the serving cells of one PUCCH group may be in different TAGs and serving cells of one TAG may be in different PUCCH groups. Configuration of PUCCH groups and TAGs may be left to eNB implementation. In another example implementation, restriction(s) on the configuration of a PUCCH cell may be specified. For example, in an example embodiment, cells in a given PUCCH group may belong to the same TAG. In an example, an sTAG may only comprise cells of one PUCCH group. In an example, one-to-one mapping between TAGs and PUCCH groups may be implemented. In implementation, cell configurations may be limited to some of the examples. In other implementations, some or all the below configurations may be allowed.

In an example embodiment, for an SCell in a pTAG, the timing reference may be a PCell. For an SCell in an sTAG, the timing reference may be any activated SCell in the sTAG. For an SCell (configured with PUCCH or not) in a pTAG, a pathloss reference may be configured to be a PCell or an SIB-2 linked SCell. For an SCell in a sTAG, the pathloss reference may be the SIB-2 linked SCell. When a TAT associated with a pTAG is expired, the TAT associated with sTAGs may be considered as expired. When a TAT of an sTAG containing PUCCH SCell expires, the MAC may indicate to an RRC to release PUCCH resource for the PUCCH group. When the TAT of an sTAG containing a PUCCH SCell is not running, the uplink transmission (PUSCH) for SCells in the secondary PUCCH group not belonging to the sTAG including the PUCCH SCell may not be impacted. The TAT expiry of an sTAG containing a PUCCH SCell may not trigger TAT expiry of other TAGs to which other SCells in the same PUCCH group belong. When the TAT associated with sTAG not containing a PUCCH SCell is not running, the wireless device may stop the uplink transmission for the SCell in the sTAG and may not impact other TAGs.

In an example embodiment, a MAC entity may have a configurable timer timeAlignmentTimer per TAG. The timeAlignmentTimer may be used to control how long the MAC entity considers the Serving Cells belonging to the associated TAG to be uplink time aligned. The MAC entity may, when a Timing Advance Command MAC control element is received, apply the Timing Advance Command for the indicated TAG; start or restart the timeAlignmentTimer associated with the indicated TAG. The MAC entity may, when a Timing Advance Command is received in a Random Access Response message for a serving cell belonging to a TAG and/orif the Random Access Preamble was not selected by the MAC entity, apply the Timing Advance Command for this TAG and start or restart the timeAlignmentTimer associated with this TAG. Otherwise, if the timeAlignmentTimer associated with this TAG is not running, the Timing Advance Command for this TAG may be applied and the timeAlignmentTimer associated with this TAG started. When the contention resolution is considered not successful, a timeAlignmentTimer associated with this TAG may be stopped. Otherwise, the MAC entity may ignore the received Timing Advance Command.

Example embodiments of the invention may enable operation of multiple PUCCH groups. Other example embodiments may comprise a non-transitory tangible computer readable media comprising instructions executable by one or more processors to cause operation of PUCCH groups. Yet other example embodiments may comprise an article of manufacture that comprises a non-transitory tangible computer readable machine-accessible medium having instructions encoded thereon for enabling programmable hardware to cause a device (e.g. wireless communicator, UE, base station, etc.) to enable operation of PUCCH groups. The device may include processors, memory, interfaces, and/or the like. Other example embodiments may comprise communication networks comprising devices such as base stations, wireless devices (or user equipment: UE), servers, switches, antennas, and/or the like. In an example embodiment one or more TAGs may be configured along with PUCCH group configuration.

FIG. 13 is an example MAC PDU as per an aspect of an embodiment of the present invention. In an example embodiment, a MAC PDU may comprise of a MAC header, zero or more MAC Service Data Units (MAC SDU), zero or more MAC control elements, and optionally padding. The MAC header and the MAC SDUs may be of variable sizes. A MAC PDU header may comprise one or more MAC PDU subheaders. A subheader may correspond to either a MAC SDU, a MAC control element or padding. A MAC PDU subheader may comprise header fields R, F2, E, LCID, F, and/or L. The last subheader in the MAC PDU and subheaders for fixed sized MAC control elements may comprise the four header fields R, F2, E, and/or LCID. A MAC PDU subheader corresponding to padding may comprise the four header fields R, F2, E, and/or LCID.

In an example embodiment, LCID or Logical Channel ID field may identify the logical channel instance of the corresponding MAC SDU or the type of the corresponding MAC control element or padding. There may be one LCID field for a MAC SDU, MAC control element or padding included in the MAC PDU. In addition to that, one or two additional LCID fields may be included in the MAC PDU when single-byte or two-byte padding is required but cannot be achieved by padding at the end of the MAC PDU. The LCID field size may be, e.g. 5 bits. L or the Length field may indicate the length of the corresponding MAC SDU or variable-sized MAC control element in bytes. There may be one L field per MAC PDU subheader except for the last subheader and subheaders corresponding to fixed-sized MAC control elements. The size of the L field may be indicated by the F field and F2 field. The F or the Format field may indicate the size of the Length field. There may be one F field per MAC PDU subheader except for the last subheader and subheaders corresponding to fixed-sized MAC control elements and expect for when F2 is set to 1. The size of the F field may be 1 bit. In an example, if the F field is included, and/or if the size of the MAC SDU or variable-sized MAC control element is less than 128 bytes, the value of the F field is set to 0, otherwise it is set to 1. The F2 or the Format2 field may indicate the size of the Length field. There may be one F2 field per MAC PDU subheader. The size of the F2 field may be 1 bit. In an example, if the size of the MAC SDU or variable-sized MAC control element is larger than 32767 bytes and if the corresponding subheader is not the last subheader, the value of the F2 field may be set to 1, otherwise it is set to 0. The E or the Extension field may be a flag indicating if more fields are present in the MAC header or not. The E field may be set to “1” to indicate another set of at least R/F2/E/LCID fields. The E field may be set to “0” to indicate that either a MAC SDU, a MAC control element or padding starts at the next byte. R or reserved bit, set to “0”.

MAC PDU subheaders may have the same order as the corresponding MAC SDUs, MAC control elements and padding. MAC control elements may be placed before any MAC SDU. Padding may occur at the end of the MAC PDU, except when single-byte or two-byte padding is required. Padding may have any value and the MAC entity may ignore it. When padding is performed at the end of the MAC PDU, zero or more padding bytes may be allowed. When single-byte or two-byte padding is required, one or two MAC PDU subheaders corresponding to padding may be placed at the beginning of the MAC PDU before any other MAC PDU subheader. In an example, a maximum of one MAC PDU may be transmitted per TB per MAC entity, a maximum of one MCH MAC PDU can be transmitted per TTI.

At least one RRC message may provide configuration parameters for at least one cell and configuration parameters for PUCCH groups. The information elements in one or more RRC messages may provide mapping between configured cells and PUCCH SCells. Cells may be grouped into a plurality of cell groups and a cell may be assigned to one of the configured PUCCH groups. There may be a one-to-one relationship between PUCCH groups and cells with configured PUCCH resources. At least one RRC message may provide mapping between an SCell and a PUCCH group, and PUCCH configuration on PUCCH SCell.

System information (common parameters) for an SCell may be carried in a RadioResourceConfigCommonSCell in a dedicated RRC message. Some of the PUCCH related information may be included in common information of an SCell (e.g. in the RadioResourceConfigCommonSCell). Dedicated configuration parameters of SCell and PUCCH resources may be configured by dedicated RRC signaling using, for example, RadioResourceConfigDedicatedSCell.

The IE PUCCH-ConfigCommon and IE PUCCH-ConfigDedicated may be used to specify the common and the UE specific PUCCH configuration respectively.

In an example, PUCCH-ConfigCommon may include: deltaPUCCH-Shift: ENUMERATED {ds1, ds2, ds3}; nRB-CQI: INTEGER (0 . . . 98); nCS-AN: INTEGER (0 . . . 7); and/or n1PUCCH-AN: INTEGER (0 . . . 2047). The parameter deltaPUCCH-Shift (Δ_(shift) ^(PUCCH)), nRB-CQI (N_(RB) ⁽²⁾), nCS-An (N_(cs) ⁽¹⁾), and n1PUCCH-AN (N_(PUCCH) ⁽¹⁾) may be physical layer parameters of PUCCH.

PUCCH-ConfigDedicated may be employed. PUCCH-ConfigDedicated may include: ackNackRepetition CHOICE{release: NULL, setup: SEQUENCE {repetitionFactor: ENUMERATED {n2, n4, n6, spare1}, n1PUCCH-AN-Rep: INTEGER (0 . . . 2047)}}, tdd-AckNackFeedbackMode: ENUMERATED {bundling, multiplexing} OPTIONAL}. ackNackRepetitionj parameter indicates whether ACK/NACK repetition is configured. n2 corresponds to repetition factor 2, n4 to 4 for repetitionFactor parameter (N_(ANRep)). n1PUCCH-AN-Rep parameter may be n_(PUCCH,ANRep) ^((1,p)) for antenna port P0 and for antenna port P1. dd-AckNackFeedbackMode parameter may indicate one of the TDD ACK/NACK feedback modes used. The value bundling may correspond to use of ACK/NACK bundling whereas, the value multiplexing may correspond to ACK/NACK multiplexing. The same value may apply to both ACK/NACK feedback modes on PUCCH as well as on PUSCH.

The parameter PUCCH-ConfigDedicated may include simultaneous PUCCH-PUSCH parameter indicating whether simultaneous PUCCH and PUSCH transmissions is configured. An E-UTRAN may configure this field for the PCell when the nonContiguousUL-RA-WithinCC-Info is set to supported in the band on which PCell is configured. The E-UTRAN may configure this field for the PSCell when the nonContiguousUL-RA-WithinCC-Info is set to supported in the band on which PSCell is configured. The E-UTRAN may configure this field for the PUCCH SCell when the nonContiguousUL-RA-WithinCC-Info is set to supported in the band on which PUCCH SCell is configured.

A UE may transmit radio capabilities to an eNB to indicate whether UE support the configuration of PUCCH groups. The simultaneous PUCCH-PUSCH in the UE capability message may be applied to both a PCell and an SCell. Simultaneous PUCCH+PUSCH may be configured separately (using separate IEs) for a PCell and a PUCCH SCell. For example, a PCell and a PUCCH SCell may have different or the same configurations related to simultaneous PUCCH+PUSCH.

The eNB may select the PUCCH SCell among current SCells or candidate SCells considering cell loading, carrier quality (e.g. using measurement reports), carrier configuration, and/or other parameters. From a functionality perspective, a PUCCH Cell group management procedure may include a PUCCH Cell group addition, a PUCCH cell group release, a PUCCH cell group change and/or a PUCCH cell group reconfiguration. The PUCCH cell group addition procedure may be used to add a secondary PUCCH cell group (e.g., to add PUCCH SCell and one or more SCells in the secondary PUCCH cell group). In an example embodiment, cells may be released and added employing one or more RRC messages. In another example embodiment, cells may be released employing a first RRC message and then added employing a second RRC messages.

SCells including PUCCH SCell may be in a deactivated state when they are configured. A PUCCH SCell may be activated after an RRC configuration procedure by an activation MAC CE. An eNB may transmit a MAC CE activation command to a UE. The UE may activate an SCell in response to receiving the MAC CE activation command.

In example embodiments, a timer is running once it is started, until it is stopped or until it expires; otherwise it may not be running. A timer can be started if it is not running or restarted if it is running. For example, a timer may be started or restarted from its initial value.

For dual connectivity, common search space may be supported in the PSCell which belongs to the SCG. A UE configured with DC is required to monitor the CSS on the pSCell for PDCCH with CRC scrambled with RA-RNTI, C-RNTI, Temporary C-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI and eIMTA-RNTI. The common search space on the PSCell may be used to transmit DCI format 3/3A, which is scrambled with TPC-PUCCH-RNTI or TPC-PUSCH-RNTI. In Rel-12 dual connectivity, CSS on pSCell may be supported. Serving cells in different cell groups may be scheduled by different eNBs connected through non-ideal backhaul.

Independent TPC in different PUCCH cell groups may be required since different PUCCH cell groups may have different payload sizes and channel conditions. Common search space may not be supported in a PUCCH SCell. RRC parameters for SCell PUCCH power control may be independent from those of PCell PUCCH. TPC commands for PUCCH on SCell may be transmitted in DCI(s) for a UE and be carried on the SCell carrying the PUCCH. The transmit power of PUCCH on SCell may be controlled by the TPC command carried by a DL assignments. For PUCCH transmission in a PUCCH cell group, the TPC carried in PDCCH/EPDCCH with DL grant transmitted on PCell or the SCell with PUCCH transmission may be employed to adjust the PUCCH transmit power in the respective PUCCH cell group.

A DCI format 3/3A for PUCCH configured on an SCell may be supported employing the common search space on the PCell. RRC signaling message(s) may indicate the configuration and parameters related to PCell common search space employed for transmission of the DCI format 3/3A TPC commands for PUCCH on PUCCH SCell.

Application of a DCI format 3/3A to the PUCCH on an SCell using the common search space of the primary cell may be implemented. TPC commands for PUCCH on SCell may be transmitted using DCI format 3/3A in the common search space in the PCell. There may be no need to support CSS on the SCell with PUCCH transmission for transmission of PUCCH TPC commands.

A DCI transports downlink or uplink scheduling information, requests for aperiodic CQI reports, notifications of MCCH change or uplink power control commands for one cell and one RNTI. The RNTI may be implicitly encoded in the CRC. The processing mechanism for one DCI may comprise: information element multiplexing, CRC attachment, channel coding, and/or rate matching.

The fields defined in the DCI formats may be mapped to the information bits a0 to aA-1 as follows. A field may be mapped in the order in which it appears in the description, including the zero-padding bit(s), if any, with the first field mapped to the lowest order information bit a0 and each successive field mapped to higher order information bits. The most significant bit of a field may be mapped to the lowest order information bit for that field, e.g. the most significant bit of the first field is mapped to a0.

In an example embodiment, a DCI format 3 may be used for the transmission of TPC commands for PUCCH and PUSCH with 2-bit power adjustments. The following information may transmitted employing the DCI format 3: TPC command number 1, TPC command number 2, . . . , TPC command number N, where

${N = \left\lfloor \frac{L_{{format}0}}{2} \right\rfloor},$

and where L_(format 0) is equal to the payload size of format 0 before CRC attachment when format 0 is mapped onto the common search space, including any padding bits appended to format 0. The parameter tpc-Index provided by higher layers determines the index to the TPC command for a given UE. If

${\left\lfloor \frac{L_{{format}0}}{2} \right\rfloor < \frac{L_{{format}0}}{2}},$

a bit of value zero shall be appended to format 3.

A DCI format 3A is used for the transmission of TPC commands for PUCCH and PUSCH with single bit power adjustments. The following information is transmitted employing the DCI format 3A: TPC command number 1, TPC command number 2, . . . , TPC command number M.

In an example embodiment, M=L_(format 0), and where L_(format 0) is equal to the payload size of format 0 before CRC attachment when format 0 is mapped onto the common search space, including any padding bits appended to format 0. The parameter tpc-Index provided by higher layers (e.g. RRC) determines the index to the TPC command for a given UE.

Error detection may be provided on DCI transmissions through a cyclic redundancy check (CRC). The payload may be employed to calculate the CRC parity bits. Denote the bits of the payload by a₀, a₁, a₂, a₃, . . . , a_(A-1), and the parity bits by p₀, p₁, p₂, p₃, . . . , p_(L-1). A is the payload size and L is the number of parity bits.

The parity bits may be computed and attached setting L to 16 bits, resulting in the sequence b₀, b₁, b₂, b₃, . . . , b_(B-1), where B=A+L.

In the case where closed-loop UE transmit antenna selection is not configured or applicable, after attachment, the CRC parity bits may be scrambled with the corresponding RNTI x_(rnti,0), x_(rnti,1), . . . , x_(rnti,15), where x_(rnti,0) corresponds to the MSB of the RNTI, to form the sequence of bits c₀, c₁, c₂, c₃, . . . , c_(B-1). The relation between ck and bk is: c_(k)=b_(k) for k=0, 1, 2, . . . , A-1; c_(k)=(b_(k)+x_(rnti,k-A))mod 2 for k=A, A+1, A+2, . . . , A+15.

In an example embodiment, in the case where closed-loop UE transmit antenna selection is configured and applicable, after attachment, the CRC parity bits with DCI format 0 may be scrambled with the antenna selection mask x_(AS,0), x_(AS,1), . . . , x_(AS,15) as indicated in Table below and the corresponding RNTI x_(rnti,0), x_(rnti,1), . . . , x_(rnti,15) to form the sequence of bits c₀, c₁, c₂, c₃, . . . , c_(B-1). The relation between ck and bk is: ck=bk for k=0, 1, 2, . . . , A-1; c_(k)=(b_(k)+x_(rnti,k-A)+x_(AS,k-A))mod 2 for k=A, A+1, A+2, . . . , A+15.

A UE transmit antenna selection mask may be defined as: When UE transmit antenna selection is UE port 0, then Antenna selection mask <x_(As,0), x_(As,1), . . . , x_(AS,15)> is <0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0>. When UE transmit antenna selection is UE port 1, then Antenna selection mask <x_(AS,0), x_(AS,1), . . . , x_(AS,15)> is <0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1>.

In an example channel coding, information bits may be delivered to the channel coding block. They may be denoted by c₀, c₁, c₂, c₃, . . . , c_(K-1), where K is the number of bits, and they may be tail biting convolutionally encoded.

After encoding the bits are denoted by d₀ ^((i)), d₁ ^((i)), d₂ ^((i)), d₃ ^((i)), . . . , d_(D-1) ^((i)), with i=0, 1, and 2, and where D is the number of bits on the i-th coded stream, i.e., D=K.

In an example rate matching, a tail biting convolutionally coded block may be delivered to the rate matching block. This block of coded bits may be denoted by d₀ ^((i)), d₁ ^((i)), d₂ ^((i)), d₃ ^((i)), . . . , d_(D-1) ^((i)), with i=0, 1, and 2, and where i is the coded stream index and D is the number of bits in each coded stream. This coded block may be rate matched. After rate matching, the bits may be denoted by e₀, e₁, e₂, e₃, . . . e_(E-1), where E is the number of rate matched bits.

The IE TPC-PDCCH-Config may be used to specify the RNTIs and indexes for PUCCH and PUSCH power control. The power control function may be setup or released with the IE. TPC-PDCCH-Config::=CHOICE {releaseNULL, setup SEQUENCE {tpc-RNTI BIT STRING (SIZE (16)), tpc-Index TPC-Index}}

In an example embodiment, TPC-Index::=CHOICE {indexOfFormat3 INTEGER (1 . . . 15), indexOfFormat3A INTEGER (1 . . . 31)}. The parameter indexOfFormat3 may indicate index of N when DCI format 3 is used. The parameter IndexOfFormat3A may indicate index of M when DCI format 3A is used. The parameter tpc-Index may indicate index of N or M, where N or M is dependent on the used DCI format (i.e. format 3 or 3a). The parameter tpc-RNTI may indicate RNTI for power control using DCI format 3/3A.

The parameter TPC-Index may indicate an index and a first downlink control information (DCI) format. The parameter TPC-Index may indicate which one of the DCI format 3 or DCI format 3A is employed for PUCCH TPC commands. The parameter TPC-Index may indicate the index of the TPC command in the corresponding DCI.

The parameter tpc-PDCCH-ConfigPUCCH is of TPC-PDCCH-Config type and indicates PDCCH configuration for power control of PUCCH using format 3/3A. The parameter tpc-PDCCH-ConfigPUSCH is of TPC-PDCCH-Config type and indicates PDCCH configuration for power control of PUSCH using format 3/3A.

In an example embodiment, PCell common search space may be employed for transmission of DCI format 3/3A power control commands for PUCCH(s). The TPC-PUCCH-RNTI value may be employed for TPC transmitted to the UE for PUCCH on a PUCCH SCell and PUCCH on a PCell. The UE may search common search space of the PCell for the TPC-PUCCH-RNTI for the TPC commands of PUCCH on a PUCCH SCell and PUCCH on a PCell. The eNB may also transmit the format of the DCI (3 or 3A) and a first index for TPC of the PUCCH on the PCell and a second index for the TPC of the PUCCH on PUCCH SCell. The second index of the DCI may be transmitted in a dedicated physical configuration parameter of an RRC message as a part of the configuration IEs of the PUCCH SCell.

In an example embodiment, a UE may search a common search space of the PCell for TPC-PUCCH-RNTI and TPC-PUSCH-RNTI. A DCI employing TPC-PUCCH-RNTI may comprise power control commands for PUCCH on PCell and/or PUCCH on a PUCCH SCell. The DCI employing TPC-PUSCH-RNTI may comprise power control commands for PUSCH on PCell. After decoding the DCI, the UE may employ the TPC in the DCI using the index number transmitted in the RRC message for the corresponding DCI configuration and uplink channel.

The example embodiments may not increase blind coding requirements in a UE. The existing RNTIs may be employed and no additional RNTI may be configured for TPC commands of the PUCCH of PUCCH SCell(s). The UE may need to employ a second index in a DCI associated with an existing RNTI, namely TPC-PUCCH-RNTI. The disclosed mechanism enables employing the current set of RNTIs and common search space blind decoding capability of a UE for TPC transmission of PUCCH of a PUCCH SCell. The solution is scalable and may be extended to include configurations including multiple PUCCH SCells. A power control for PUCCH resources of a PUCCH SCell or PCell is identified by a separate index on the DCI format 3 or 3A. Multiple indexes may be configured for multiple PUCCH resources on different cells.

In an example embodiment, a wireless device may receive, from a first base station, at least one message comprising configuration parameters of a plurality of cells. The plurality of cells may be grouped into a plurality of physical uplink control channel (PUCCH) cell groups comprising: a primary PUCCH group comprising a primary cell with a primary PUCCH transmitted to the first base station; and a secondary PUCCH group comprising a PUCCH secondary cell with a secondary PUCCH transmitted to the first base station. The at least one message may comprise a transmit power control (TPC) radio network temporary identifier (RNTI) and a primary TPC index for the primary PUCCH and a secondary TPC index for the secondary PUCCH.

In an example embodiment, the wireless device may search a common search space of the primary cell for at least one downlink control information (DCI) associated with at least TPC RNTI for PUCCH(s). The wireless device may adjust uplink signal transmission power of the secondary PUCCH employing a second TPC command if a DCI associated with the TPC RNTI is found. The DCI may comprise an array (sequence) of TPC commands. The secondary TPC index may determine the second TPC command in the array. The secondary TPC RNTI and the secondary TPC index may be included in a dedicated physical configuration information element (IE) for configuring the PUCCH secondary cell.

In an example embodiment, the wireless device may search a common search space of the primary cell for at least one downlink control information (DCI) associated with at least TPC RNTI for PUCCH(s). The wireless device may adjust uplink signal transmission power of the secondary PUCCH employing a second TPC command if a DCI associated with the TPC RNTI is found and the PUCCH SCell is activated. The DCI may comprise an array (sequence) of TPC commands. The secondary TPC index may determine the second TPC command in the array. The secondary TPC RNTI and the secondary TPC index may be included in a dedicated physical configuration information element (IE) for configuring the PUCCH secondary cell.

FIG. 14 is an example flow diagram as per an aspect of an embodiment of the present invention. A wireless device may receive at least one message from a base station at 1410. The message may comprise: configuration parameters of a plurality of cells, a transmit power control (TPC) radio network temporary identifier (RNTI), a primary TPC index, and/or a secondary TPC index. The plurality of cells may comprise a primary cell and/or a PUCCH secondary cell. The primary cell may comprise a primary physical uplink control channel (PUCCH) transmitted to a base station. The PUCCH secondary cell may comprise a secondary PUCCH transmitted to the base station. The primary TPC index may be for the primary PUCCH. The primary TPC index may indicate a first downlink control information (DCI) format. The secondary TPC index may be for the secondary PUCCH. The secondary TPC index may indicate the first DCI format. The secondary TPC index may have a different index value from the primary TPC index. The format of the secondary TPC index and the primary TPC index may be the same.

At 1420, the wireless device may search a common search space of the primary cell for a DCI associated with the TPC RNTI. The DCI may be of the first DCI format and comprise an array of TPC commands. The TPC commands may comprise a first TPC command and a second TPC command. The primary TPC index may identify the first TPC command in the array. The secondary TPC index may identify the second TPC command in the array. An uplink transmission power of the primary PUCCH may be adjusted employing the primary TPC command when the DCI is found. At 1430, an uplink transmission power of the secondary PUCCH may be adjusted employing the second TPC command when the DCI is found (when the PUCCH secondary cell is activated).

In an example, the first DCI format may indicate that a number between 1 to 15 is employed as the TPC index value. In an example, the first DCI format may indicate that a number between 1 to 31 is employed as the TPC index value. According to an embodiment, the primary TPC index may identify the first TPC command in the array. According to an embodiment, the wireless device may adjust uplink signal transmission power of the primary PUCCH employing the first TPC command when the DCI is found. According to an embodiment, the searching may include blind decoding for the DCI having the first DCI format. In an example, a TPC command may be encoded by two bits when a first DCI format is employed. In an example, a TPC command may be encoded by one bit when a second DCI format is employed. According to an embodiment, the DCI may be encoded employing a cyclic redundancy check.

FIG. 14 is an illustrative of an embodiment where a wireless device may receive at least one message from a base station at 1410. The message may comprise: configuration parameters of a plurality of cells, a transmit power control (TPC) radio network temporary identifier (RNTI), a primary TPC index, and/or a secondary TPC index. The plurality of cells may comprise a primary cell and/or a PUCCH secondary cell. The primary cell may comprise a primary PUCCH. The PUCCH secondary cell may comprise a secondary. The primary TPC index may be for the primary PUCCH. The secondary TPC index may be for the secondary PUCCH. At 1420, the wireless device may search a common search space of the primary cell for a DCI associated with the TPC RNTI. The DCI may comprise an array of TPC commands. The secondary TPC index may identify a TPC command in the array. At 1430, an uplink transmission power of the secondary PUCCH may be adjusted employing the second TPC command when the DCI is found. According to an embodiment, the plurality of cells may be grouped into a plurality of PUCCH groups comprising: a primary PUCCH group comprising the primary cell, and a secondary PUCCH group comprising the PUCCH secondary cell. According to an embodiment, a first format of a TPC index may indicate that one of the following is used as the TPC index value: a number between 1 to 15, a number between 1 to 31, and/or the like. According to an embodiment, the primary TPC index may identify a first TPC command in the array. According to an embodiment, the wireless device may further adjust uplink signal transmission power of the primary PUCCH employing the first TPC command when the DCI is found. According to an embodiment, the searching may comprise blind decoding for the DCI having a first format. According to an embodiment, the TPC command may be encoded by two bits when a first DCI format is employed, and the TPC command may be encoded by one bit when a second DCI format is employed. According to an embodiment, the DCI may be encoded employing a cyclic redundancy check.

FIG. 15 is an example flow diagram as per an aspect of an embodiment of the present invention. A base station may transmit at least one message to a wireless device at 1510. The message may comprise: configuration parameters of a plurality of cells, a transmit power control (TPC) radio network temporary identifier (RNTI), a primary TPC index, and/or a secondary TPC index. The plurality of cells may comprise a primary cell and/or a PUCCH secondary cell. The primary cell may comprise a primary physical uplink control channel (PUCCH) received by the base station. The PUCCH secondary cell may comprise a secondary PUCCH received by the base station. The primary TPC index may be for the primary PUCCH. The primary TPC index may indicate a first downlink control information (DCI) format. The secondary TPC index may be for the secondary PUCCH. The secondary TPC index may indicate the first DCI format. The secondary TPC index may have a different index value from the primary TPC index. The secondary TPC index may have the same DCI format as the primary TPC index

At 1520, the base station may transmit in a common search space of the primary cell, a DCI associated with the TPC RNTI. The DCI may be of the first DCI format. The DCI may comprise an array of TPC commands comprising a first TPC command and a second TPC command. The secondary TPC index may identify a TPC command in the array.

At 1530, the base station may receive the secondary PUCCH from the wireless device. The uplink transmission power of the secondary PUCCH may be adjusted employing the TPC command (when PUCCH secondary cell is activated).

FIG. 15 is illustrative of an embodiment where a base station may transmit at least one message to a wireless device at 1510. The message may comprise: configuration parameters of a plurality of cells, a transmit power control (TPC) radio network temporary identifier (RNTI), a primary TPC index, and/or a primary TPC index. The plurality of cells may comprise a primary cell and/or a PUCCH secondary cell. The primary cell may comprise a primary PUCCH. The PUCCH secondary cell may comprise a secondary PUCCH. The primary TPC index may be for the primary PUCCH. The secondary TPC index may be for the secondary PUCCH. At 1520, the base station may transmit in a common search space of the primary cell for a downlink control information (DCI) associated with the TPC RNTI. The DCI may comprise an array of TPC commands. The secondary TPC index may identify a TPC command in the array. At 1530, the base station may receive the secondary PUCCH from the wireless device. The uplink transmission power of the secondary PUCCH may be adjusted employing the TPC command.

FIG. 16 is an example flow diagram as per an aspect of an embodiment of the present invention. According to another embodiment, a wireless device may receive at least one message from a base station at 1610. The message may comprise: configuration parameters of a plurality of cells, a transmit power control (TPC) radio network temporary identifier (RNTI), a primary TPC index, and/or a secondary TPC index. The plurality of cells may comprise a primary cell and/or a PUCCH secondary cell. The primary cell may comprise a primary PUCCH. The PUCCH secondary cell may comprise a secondary PUCCH. The primary TPC index may be for the primary PUCCH. The secondary TPC index may be for the secondary PUCCH. At 1620, the wireless device may search a common search space of the primary cell for a DCI associated with the TPC RNTI. The DCI may comprise an array of TPC commands. The secondary TPC index may determine a TPC command in the array. At 1630, when the DCI is found, the wireless device may adjust uplink signal transmission power of the secondary PUCCH according to the TPC command only if the PUCCH secondary cell is activated. According to an embodiment, the plurality of cells may be grouped into a plurality of PUCCH groups comprising: a primary PUCCH group comprising the primary cell, and a secondary PUCCH group comprising the PUCCH secondary cell. According to an embodiment, the primary TPC index may determine a first TPC command in the array. According to an embodiment, the wireless device may further adjust uplink signal transmission power of the primary PUCCH employing the first TPC command when the DCI is found. According to an embodiment, the TPC command may be encoded by two bits when a first DCI format is employed, and the TPC command is encoded by one bit when a second DCI format is employed.

A primary PUCCH group may comprise a group of serving cells including a PCell whose PUCCH signaling may be associated with the PUCCH on the PCell. A PUCCH group may comprise either a primary PUCCH group and/or a secondary PUCCH group. A PUCCH SCell may comprise a Secondary Cell configured with a PUCCH. A secondary PUCCH group may comprise a group of SCells whose PUCCH signalling is associated with the PUCCH on the PUCCH SCell. A Timing Advance Group may comprise a group of serving cells configured by and RRC and that, for the cells with an UL configured, use the same timing reference cell and/or the same Timing Advance value. A Primary Timing Advance Group may comprise a Timing Advance Group containing the PCell. A Secondary Timing Advance Group may comprise a Timing Advance Group not containing the PCell. A PUCCH may be transmitted on a PCell, a PUCCH SCell (if such is configured in CA) and/or on a PSCell (in DC).

In an example embodiment, a IE TPC-PDCCH-Config may be employed to specify the RNTIs and indexes for PUCCH and PUSCH power control. The power control function may either be setup and/or released with the IE. A TPC-PDCCH-Config information element may be described by ASN1START—TPC-PDCCH-Config::=CHOICE {release NULL, setup SEQUENCE {tpc-RNTI BIT STRING (SIZE (16)), tpc-Index TPC-Index}} TPC-PDCCH-ConfigSCell::=CHOICE {release NULL, setup SEQUENCE {tpc-Index-PUCCH-SCell-r13 TPC-Index}} TPC-Index::=CHOICE {indexOfFormat3 INTEGER (1 . . . 15), indexOfFormat3A INTEGER (1 . . . 31)}—ASN1STOP. An IndexOfFormat3 may comprise an index of N when DCI format 3 is used. An IndexOfFormat3A may comprise an index of M when DCI format 3A is used. A tpc-Index may comprise an index of N or M, where N or M may be dependent on the used DCI format (i.e. format 3 or 3a). A tpc-Index-PUCCH-SCell may comprise an index of N or M, where N or M may be dependent on the used DCI format (i.e. format 3 or 3a). A tpc-RNTI may comprise an RNTI for power control using DCI format 3/3A.

DCI format 3 may be employed for the transmission of TPC commands for PUCCH and PUSCH with 2-bit power adjustments. The following information, without limitation, may be transmitted by means of the DCI format 3: TPC command number 1; TPC command number 2, . . . ; TPC command number N, where N=Lformat 0/2, and where Lformat0 may be equal to the payload size of format 0 before CRC attachment when format 0 is mapped onto a common search space, including any padding bits appended to format 0. The parameter tpc-Index and/or tpc-Index-PUCCH-SCell-r13 provided by higher layers may determine the index to the TPC command for a given UE. If |Lformat 0/2|<Lformat 0/2, a bit of value zero may be appended to format 3.

DCI format 3A may be employed for the transmission of TPC commands for PUCCH and PUSCH with single bit power adjustments. The following information, without limitation, may be transmitted by means of the DCI format 3A:—TPC command number 1; TPC command number 2; . . . ; TPC command number M, where M=Lformat 0, and where Lformat 0 may be equal to the payload size of format 0 before CRC attachment when format 0 is mapped onto the common search space, including any padding bits appended to format 0. The parameter tpc-Index and/or tpc-Index-PUCCH-SCell-r13 provided by higher layers may determine the index to the TPC command for a given UE.

With respect to Physical uplink control channel UE behavior, if serving cell c is the primary cell, for PUCCH format 1/1a/1b/2/2a/2b/3, the setting of the UE Transmit power P_(PUCCH) for the physical uplink control channel (PUCCH) transmission in subframe i for serving cell c may be defined by:

$\begin{matrix} {{{P_{PUCCH}(i)} = {\min{\begin{Bmatrix} {{P_{{CMAX},c}(i)},} \\ \begin{matrix} {P_{0{\_{PUCCH}}} + {PL}_{c} + {h\left( {n_{CQI},n_{HARQ},n_{SR}} \right)} +} \\ {{\Delta_{F\_{PUCCH}}(F)} + {\Delta_{TxD}\left( F^{\prime} \right)} + {g(i)}} \end{matrix} \end{Bmatrix}\lbrack{dBm}\rbrack}}}{{g(i)} = {{g\left( {i - 1} \right)} + {\overset{M - 1}{\sum\limits_{m = 0}}{\delta_{PUCCH}\left( {i - k_{m}} \right)}}}}} &  \end{matrix}$

where g(i) is the current PUCCH power control adjustment state and where g(0) is the first value after reset. TPC Command Field in DCI format 1A/1B/1D/1/2A/2B/2C/2D/2/3 may be 0, 1, 2, and 3 respectively corresponding to δ_(PUCCH) [dB] of −1, 0, 1, 3.

The δ_(PUCCH) dB values signalled on PDCCH with DCI format 3/3A may be given as semi-statically configured by higher layers described here. TPC Command Field in DCI format 3A may be 0 and 1 respectively corresponding to δ_(PUCCH) [dB] of −1 and 1.

In this specification, “a” and “an” and similar phrases are to be interpreted as “at least one” and “one or more.” In this specification, the term “may” is to be interpreted as “may, for example.” In other words, the term “may” is indicative that the phrase following the term “may” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. If A and B are sets and every element of A is also an element of B, A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B={cell1, cell2} are: {cell1}, {cell2}, and {cell1, cell2}.

In this specification, parameters (Information elements: IEs) may comprise one or more objects, and each of those objects may comprise one or more other objects. For example, if parameter (IE) N comprises parameter (IE) M, and parameter (IE) M comprises parameter (IE) K, and parameter (IE) K comprises parameter (information element) J, then, for example, N comprises K, and N comprises J. In an example embodiment, when one or more messages comprise a plurality of parameters, it implies that a parameter in the plurality of parameters is in at least one of the one or more messages, but does not have to be in each of the one or more messages.

Many of the elements described in the disclosed embodiments may be implemented as modules. A module is defined here as an isolatable element that performs a defined function and has a defined interface to other elements. The modules described in this disclosure may be implemented in hardware, software in combination with hardware, firmware, wetware (i.e. hardware with a biological element) or a combination thereof, all of which are behaviorally equivalent. For example, modules may be implemented as a software routine written in a computer language configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, Matlab or the like) or a modeling/simulation program such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript. Additionally, it may be possible to implement modules using physical hardware that incorporates discrete or programmable analog, digital and/or quantum hardware. Examples of programmable hardware comprise: computers, microcontrollers, microprocessors, application-specific integrated circuits (ASICs); field programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs). Computers, microcontrollers and microprocessors are programmed using languages such as assembly, C, C++ or the like. FPGAs, ASICs and CPLDs are often programmed using hardware description languages (HDL) such as VHSIC hardware description language (VHDL) or Verilog that configure connections between internal hardware modules with lesser functionality on a programmable device. Finally, it needs to be emphasized that the above mentioned technologies are often used in combination to achieve the result of a functional module.

The disclosure of this patent document incorporates material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, for the limited purposes required by law, but otherwise reserves all copyright rights whatsoever.

While various embodiments have been described above, it should be understood that they have been presented by way of example, and not limitation. It will be apparent to persons skilled in the relevant art(s) that various changes in form and detail can be made therein without departing from the spirit and scope. In fact, after reading the above description, it will be apparent to one skilled in the relevant art(s) how to implement alternative embodiments. Thus, the present embodiments should not be limited by any of the above described exemplary embodiments. In particular, it should be noted that, for example purposes, the above explanation has focused on the example(s) using FDD communication systems. However, one skilled in the art will recognize that embodiments of the invention may also be implemented in a system comprising one or more TDD cells (e.g. frame structure 2 and/or frame structure 3-licensed assisted access). The disclosed methods and systems may be implemented in wireless or wireline systems. The features of various embodiments presented in this invention may be combined. One or many features (method or system) of one embodiment may be implemented in other embodiments. Only a limited number of example combinations are shown to indicate to one skilled in the art the possibility of features that may be combined in various embodiments to create enhanced transmission and reception systems and methods.

In addition, it should be understood that any figures which highlight the functionality and advantages, are presented for example purposes only. The disclosed architecture is sufficiently flexible and configurable, such that it may be utilized in ways other than that shown. For example, the actions listed in any flowchart may be re-ordered or only optionally used in some embodiments.

Further, the purpose of the Abstract of the Disclosure is to enable the U.S. Patent and Trademark Office and the public generally, and especially the scientists, engineers and practitioners in the art who are not familiar with patent or legal terms or phraseology, to determine quickly from a cursory inspection the nature and essence of the technical disclosure of the application. The Abstract of the Disclosure is not intended to be limiting as to the scope in any way.

Finally, it is the applicant's intent that only claims that include the express language “means for” or “step for” be interpreted under 35 U.S.C. 112, paragraph 6. Claims that do not expressly include the phrase “means for” or “step for” are not to be interpreted under 35 U.S.C. 112. 

What is claimed is:
 1. A base station comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the base station to: transmit, to a wireless device, at least one message comprising: configuration parameters of a plurality of cells comprising: a primary cell with a primary physical uplink control channel (PUCCH); and a PUCCH secondary cell with a secondary PUCCH; a transmit power control (TPC) radio network temporary identifier (RNTI); a primary TPC index for the primary PUCCH; and a secondary TPC index for the secondary PUCCH; transmit an activation control element indicating activation of the PUCCH secondary cell; transmit, via a common search space of the primary cell, a downlink control information (DCI) associated with the TPC RNTI, wherein: the DCI comprises an array of TPC commands; and the secondary TPC index determines a TPC command in the array; and receive, from the wireless device and via the secondary PUCCH, an uplink signal.
 2. The base station of claim 1, wherein the plurality of cells are grouped into a plurality of PUCCH groups comprising: a primary PUCCH group comprising the primary cell; and a secondary PUCCH group comprising the PUCCH secondary cell.
 3. The base station of claim 2, wherein: the primary TPC index indicates a first DCI format; the secondary TPC index indicates the first DCI format; the secondary TPC index has a TPC index value different from that of the primary TPC index; and the DCI is of the first DCI format.
 4. The base station of claim 3, wherein: the array of TPC commands comprises the TPC command and a first TPC command; and the primary TPC index identifies the first TPC command in the array.
 5. The base station of claim 1, wherein the primary TPC index determines a first TPC command in the array.
 6. The base station of claim 5, wherein the instructions, when executed by the one or more processors, further cause the base station to receive, from the wireless device and via the primary PUCCH, a second uplink signal.
 7. The wireless device of claim 1, wherein: the TPC command is encoded by two bits when a first DCI format is employed; and the TPC command is encoded by one bit when a second DCI format is employed.
 8. A base station comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the base station to: transmit, to a wireless device, at least one message comprising: configuration parameters of a plurality of cells comprising: a primary cell with a primary physical uplink control channel (PUCCH); and a PUCCH secondary cell with a secondary PUCCH; a transmit power control (TPC) radio network temporary identifier (RNTI); a primary TPC index for the primary PUCCH; and a secondary TPC index for the secondary PUCCH; transmit, via a common search space of the primary cell, a downlink control information (DCI) associated with the TPC RNTI, wherein: the DCI comprises an array of TPC commands; and the secondary TPC index identifies a TPC command in the array; and receive, from the wireless device and via the secondary PUCCH, an uplink signal.
 9. The base station of claim 8, wherein the plurality of cells are grouped into a plurality of PUCCH groups comprising: a primary PUCCH group comprising the primary cell; and a secondary PUCCH group comprising the PUCCH secondary cell.
 10. The base station of claim 9, wherein: the primary TPC index indicates a first DCI format; the secondary TPC index indicates the first DCI format; the secondary TPC index has a TPC index value different from that of the primary TPC index; and the DCI is of the first DCI format.
 11. The base station of claim 10, wherein: the array of TPC commands comprises the TPC command and a first TPC command; and the primary TPC index identifies the first TPC command in the array.
 12. The base station of claim 8, wherein a first format of a TPC index indicates that one of the following is used as a TPC index value: a number between 1 to 15; and a number between 1 to
 31. 13. The base station of claim 8, wherein the primary TPC index identifies a first TPC command in the array.
 14. The base station of claim 13, wherein the instructions, when executed by the one or more processors, further cause the base station to receive, from the wireless device and via the primary PUCCH, a second uplink signal.
 15. The base station of claim 8, wherein the DCI is scrambled employing the TPC RNTI.
 16. The base station of claim 8, wherein: the TPC command is encoded by two bits when a first DCI format is employed; and the TPC command is encoded by one bit when a second DCI format is employed.
 17. The method of claim 8, wherein the DCI is encoded employing a cyclic redundancy check.
 18. A base station comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the base station to: transmit, to a wireless device, at least one message comprising: configuration parameters of a plurality of cells, the plurality of cells grouped into a plurality of physical uplink control channel (PUCCH) groups comprising: a primary PUCCH group comprising a primary cell with a primary PUCCH transmitted to the base station; and a secondary PUCCH group comprising a PUCCH secondary cell with a secondary PUCCH transmitted to the base station; a transmit power control (TPC) radio network temporary identifier (RNTI); a primary TPC index for the primary PUCCH, the primary TPC index indicates a first downlink control information (DCI) format; and a secondary TPC index for the secondary PUCCH, the secondary TPC index indicates the first DCI format and having a different index value from the primary TPC index; transmit, via a common search space of the primary cell, a DCI associated with the TPC RNTI, wherein: the DCI is of the first DCI format and comprises an array of TPC commands comprising a first TPC command and a second TPC command; and the secondary TPC index identifies the second TPC command in the array; and receive, from the wireless device and via the secondary PUCCH, an uplink signal.
 19. The base station of claim 18, wherein the first DCI format indicates that one of the following is employed as a TPC index value: a number between 1 to 15; and a number between 1 to
 31. 20. The base station of claim 18, wherein the primary TPC index identifies the first TPC command in the array.
 21. The base station of claim 20, wherein the instructions, when executed by the one or more processors, further cause the base station to receive, from the wireless device and via the primary PUCCH, a second uplink signal.
 22. The base station of claim 18, wherein the DCI is scrambled employing the TPC RNTI.
 23. The base station of claim 18, wherein: the second TPC command is encoded by two bits when the first DCI format is employed; and the second TPC command is encoded by one bit when a second DCI format is employed.
 24. The base station of claim 18, wherein the DCI is encoded employing a cyclic redundancy check. 